Newly added hosts to BIND...
Newly added hosts to BIND take long for other computer beeing found.
So what do I need to "propagate" them faster to other OS? My Zone file: Code:
$ttl 38400 |
Hi,
If you add a new host in a zone, that host is not cached anywhere, so it can be resolved immediately from clients using your dns. So, do you remember to increase the serial number and reload bind after adding/editing hosts? Regards |
Quote:
don't know anything about a serial number (using webmin) but I definitely reloaded BIND after adding a host. Still needs approx. 15 minutes to be available. |
Quote:
Anyway a new host should be resolvable immediately after been added in the zone file, either from the nameserver and from the clients, because it's not cached. Add a new host and see what gives: Code:
dig new-host.local @x.x.x.x |
Problem is: After reboot of the client (and hence the server too because it's a VM) it takes approx. 15 minutes before the addresses the DNS handles can be resolved.
|
Quote:
Once named is up and running, the dns can resolve whatever domain it's authoritative for. |
Hmmm...
Some other networking problem? Sounds reasonable. What comes to your mind looking at my situation? |
Quote:
The fact is that once bind is up and running, the dns resolution should not be a problem |
Quote:
|
Quote:
Try nslookup or better dig as it gives more details: Code:
dig new-host.local @x.x.x.x |
This is from dig:
Code:
; <<>> DiG 9.9.2-P1 <<>> www.zf-template.loc |
Quote:
Also what you mean by "I cannot ping www.zf-template.loc"? When you run: Code:
ping www.zf-template.loc |
Quote:
Very strange. |
Quote:
You can dig the host www.zf-template.loc and get its IP address from a client, but right after that pinging that host from the same client you get a "host unkown"? What's in the client /etc/resolv.conf and /etc/nsswitch.conf? |
In this special case the host is running on Windows 7 but dig and ping from other Linux hosts gives the same result.
|
All times are GMT -5. The time now is 03:55 AM. |