LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 05-15-2013, 09:34 PM   #1
psycroptic
Member
 
Registered: Aug 2011
Location: USA
Distribution: ArchLinux - 3.0 kernel
Posts: 349

Rep: Reputation: Disabled
Windows clients fail to resolve un-FQDN'd hostname after a random amount of time


I have an archlinux server (hostname "pLAN9-Server1" here) setup with dhcpd and BIND for a local network. The server also hosts files via samba. After what seems like a random amount of time, all Windows clients stop being able to ping or access the server itself when they try to access it by hostname only e.g. pinging "pLAN9-Server1" fails, while pinging "pLAN9-Server1.pLAN9.site" works, pLAN9.site being the local domain. Accessing by IP address always works. This problem only affects Windows clients, and all are Windows 7 here. Linux clients are unaffected. Running an "ipconfig /renew" on the Windows machines fixes the problem for a time, but eventually it comes back.

My theory was that NetBIOS might be interfering, but disabling netbios on the clients & the samba server had no effect.

the relevant files:

/etc/named.conf
Code:
options {
        directory "/var/named";
        pid-file "/var/run/named/named.pid";
        auth-nxdomain yes;
        datasize default;
// Uncomment these to enable IPv6 connections support
// IPv4 will still work:
//      listen-on-v6 { any; };
// Add this for no IPv4:
//      listen-on { none; };

        // Default security settings.
        allow-recursion { 127.0.0.1; 172.16.16.0/16; };
        allow-transfer { none; };
        allow-update { 127.0.0.1; 172.16.16.0/16; };
        allow-query { 127.0.0.1; 172.16.16.0/16; };
        forwarders { 208.67.222.222; 208.67.222.222; };
        listen-on { 127.0.0.1; 172.16.16.2; };
#       edns-udp-size 512;
        edns-udp-size 4096 ;
    version none;
    hostname none;
    server-id none;
};

zone "localhost" IN {
        type master;
        file "localhost.zone";
        allow-transfer { any; };
};

zone "0.0.127.in-addr.arpa" IN {
        type master;
        file "127.0.0.zone";
        allow-transfer { any; };
};

zone "." IN {
        type hint;
        file "root.hint";
};

zone "pLAN9.site" IN {
        type master;
        file "pLAN9.zone";
};

zone "16.16.172.in-addr.arpa" IN {
        type master;
        file "pLAN9.rev";
};

//zone "example.org" IN {
//      type slave;
//      file "example.zone";
//      masters {
//              192.168.1.100;
//      };
//      allow-query { any; };
//      allow-transfer { any; };
//};

logging {
        channel xfer-log {
                file "/var/log/named.log";
                print-category yes;
                print-severity yes;
                print-time yes;
                severity info;
        };
        category xfer-in { xfer-log; };
        category xfer-out { xfer-log; };
        category notify { xfer-log; };
};
/var/named/pLAN9.zone

Code:
$TTL 4w
$ORIGIN pLAN9.site.
@ IN SOA pLAN9-Server1.pLAN9.site. root.pLAN9.site. (
        2012111102
        8H
        2H
        4W
        1D)

 IN NS pLAN9-Server1.pLAN9.site.
 IN MX 10 mail

pLAN9-Gateway   A       172.16.16.1
pLAN9-Server1   A       172.16.16.2
mail            A       172.16.16.2
pLAN9-Server2   A       172.16.16.3
pLAN9-Wil       A       172.16.16.10
pLAN9-HTPC      A       172.16.16.11
pLAN9-Laptop    A       172.16.16.12
Galt-PC         A       172.16.16.15
pLAN9-Switch    A       172.16.16.19
HP102E6C        A       172.16.16.253
pLAN9-WAP       A       172.16.16.254
/var/named/pLAN9.rev
Code:
$TTL 4w
@ IN SOA pLAN9-Server1.pLAN9.site. root.pLAN9.site. (
        2012111102
        8H
        2H
        4W
        1D)

        IN NS pLAN9-Server1.pLAN9.site.

1       PTR     pLAN9-Gateway.pLAN9.site.
2       PTR     pLAN9-Server1.pLAN9.site.
3       PTR     pLAN9-Server2.pLAN9.site.
10      PTR     pLAN9-Wil.pLAN9.site.
11      PTR     pLAN9-HTPC.pLAN9.site.
12      PTR     pLAN9-Laptop.pLAN9.site.
15      PTR     Galt-PC.pLAN9.site.
19      PTR     pLAN9-Switch.pLAN9.site.
253     PTR     HP102E6C.pLAN9.site.
254     PTR     pLAN9-WAP.pLAN9.site.
/etc/dhcpd.conf
Code:
option domain-name "pLAN9.site";
option domain-name-servers 172.16.16.2,208.67.222.222,208.67.220.220;
option routers 172.16.16.1;
option wpad code 252 = text;
option wpad "\n\000";

default-lease-time 604800;
min-lease-time 604800;
max-lease-time 604800;
authoritative;
log-facility local7;




subnet 172.16.0.0 netmask 255.255.0.0 {
        range 172.16.16.50 172.16.16.250;
}


# ======================== STATIC LEASES =========================

host pLAN9-Wil {
        hardware ethernet 00:1F:C6:E4:99:6B;
        fixed-address 172.16.16.10;
}

host pLAN9-HTPC {
        hardware ethernet 00:23:54:44:74:39;
        fixed-address 172.16.16.11;
}

host pLAN9-Laptop {
        hardware ethernet 00:90:F5:BB:6A:34;
        fixed-address 172.16.16.12;
}

host pLAN9-Laptop-WiFi {
        hardware ethernet 68:A3:C4:50:AB:00;
        fixed-address 172.16.16.13;
}

host Galt-PC {
        hardware ethernet 9c:b7:0d:4b:3c:19;
        fixed-address 172.16.16.15;
}

host Switch {
        hardware ethernet 64:d8:14:5d:74:bc;
        fixed-address 172.16.16.19;
}



host HP102E6C {
        hardware ethernet b4:99:ba:10:2e:6c;
        fixed-address 172.16.16.253;
}
bump

Last edited by psycroptic; 05-22-2013 at 06:24 PM. Reason: bump
 
Old 05-22-2013, 06:25 PM   #2
psycroptic
Member
 
Registered: Aug 2011
Location: USA
Distribution: ArchLinux - 3.0 kernel
Posts: 349

Original Poster
Rep: Reputation: Disabled
bump
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Resolve hostname between openvpn clients SystemR89 Linux - Server 5 07-11-2019 03:18 PM
How I can resolve the error Postfix? warning: hostname does not resolve to address kanzer Linux - Server 1 03-22-2013 08:56 AM
clients CAN resolve hostname of server w/nslookup, but CANNOT access by hostname WTF? psycroptic Linux - Networking 9 11-10-2012 11:24 AM
x-windows fails over ssh after a certain amount of time zugvogel Linux - Desktop 5 01-11-2010 09:16 PM
windows does not resolve linux hostname abrb220 Linux - Networking 6 05-18-2004 04:11 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 11:10 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration