Bind9 dns zone not updating
For example, pop.example.com, could both point to the primary server where the mail server and the business intranet reside, and the domain could be It's easy to remember that these two services are running on the same machine whose IP address is 192.168.0.1.I'm running a BIND9/Ubuntu DNS server on Amazon EC2.The DNS server was working great, until I decided to change the IP address on the server to a different one (using the elastic IP system.) Any ways I changed all of the "A", "NS", etc. I've ran the following command: And it still returns the old IP address of the name server, plus the previous two IP addresses the zone used. Is there any thing I can do at the domain registrar level?You could always go and modify the host configuration for all the users, but that would be time consuming and inconvenient.We get internet access through an xxxbox (192.168.1.1), two DNS servers provided by our ISP (.2, .129).
If it's authoritative 'aa' flag in the header will be set in the answer received ('aa' is authoritative answer). flags: qr aa rd Since 'aa' is set in the answer, then both the nameservers of provide authoritative answer.
Now imagine that our network administrator decides for some reason or another to move the mail server to the machine 192.168.0.11.
The only thing that has to be changed is the DNS server configuration file.
Your registrar may decide to test new servers for compliance to the DNS standards before applying the change.
While it is done automatically it still could take some time.
The Domain Name System (DNS) is a hierarchical naming system built on a distributed database for computers, services, or any resource connected to the Internet or a private network.