Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I changed the ip to one host on my lan and it won't resolve. I restarted bind thinking it would automatically start resolving for the machine I changed the ip address on. Does this have something to do with the value in refresh in one of the files? If that's the case, I'm assuming there's a cache somewhere. If so, how could I change it right away without waiting? Thanks in advance.
restarting BIND does flush the cache out, so that's not your problem. what your problem seems to be is that you just change an IP address on a box without reflecting the change in BIND's zone files. how is BIND supposed to know your address has changed? you coul dbe doin gthis with automated updates via DHCP, but i'd assume this is not the case from the way you have asked the question.
sorry I wasn' tclear. I did change the ip address in bind. it just won't resolve properly when I try to ping the host. The problem is something like this:
dig earth.antilogy.net: this resolves to the correct address.
ping earth.antilogy.net: this resolves to 192.168.1.4 (should be *.*.*.3
that would suggest a local cache issue. by definition a BIND server isn't going to cache a name that it holds a zone file for. what happens if you do a full zone transfer on your domain - "dig antilogy.net axfr @bindipaddresshere" that'll dump the authoritative zone file right on your lap if BIND allows it.
everything I do through dns (host earth, dig earth, etc) will turn up correctly. the zone transfer showed everything correctly, but a simple ping will show the last octet as .4 instead of .3. My dns server is also a bridge so the interface's name is "venus". I can't get the machine "earth" to resolve either so my windows box is useless for any kind of internet usage. I've looked through every zone file and they all show earth as 192.168.1.3. Dunno what the deal is. Thanks for your help though.
Does your /etc/hosts file possibly contain the original .3 entry? Ping will use your systems resolver lib configuration (usually hosts/bind), while dig only uses bind.
As for your winders box...
1) check that its DNS config is pointing to the correct address
2) type: "ipconfig /flushdns" in a command prompt
3) try disabling the "DNS client" service
I'm not at home right now, but come to think of it I think I do have the hosts file with that windows box set with the ip address that's causing the problem. Thanks a bunch.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.