BIND Slaves with forward only

CyberIT · 09-17-2020, 05:33 PM

Hello
Im having some weird activity happening on my BIND slaves running BIND 9.11.4.

I have the servers configured to be slaves for all my zones on domain.com.
I also have a few zones setup to be a forwarder for another domain and when a lookup is done it takes at least 1hr for it to resolve proper.

Code:

zone "example.com" {
    type forward;
    forward only;
    forwarders { 172.16.16.15; 172.17.16.15; };
};

If a DNS entry is updated or removed from the example.com zone and a lookup is done from a server on domain.com it shows the entry either still with the old IP or still in DNS when it is supposed to be either updated or removed.

It looks like it is either being cached somewhere but all our linux servers dont have cache enabled. Im not sure why it takes a long time to update DNS when trying to do a lookup from domain.com to example.com.

Any help would be greatly appreciated.

Thank you!

bathory · 09-18-2020, 01:45 AM

Quote:

Originally Posted by CyberIT

Hello
Im having some weird activity happening on my BIND slaves running BIND 9.11.4.

I have the servers configured to be slaves for all my zones on domain.com.
I also have a few zones setup to be a forwarder for another domain and when a lookup is done it takes at least 1hr for it to resolve proper.

Code:

zone "example.com" {
    type forward;
    forward only;
    forwarders { 172.16.16.15; 172.17.16.15; };
};

If a DNS entry is updated or removed from the example.com zone and a lookup is done from a server on domain.com it shows the entry either still with the old IP or still in DNS when it is supposed to be either updated or removed.

It looks like it is either being cached somewhere but all our linux servers dont have cache enabled. Im not sure why it takes a long time to update DNS when trying to do a lookup from domain.com to example.com.

Any help would be greatly appreciated.

Thank you!

Take a look at the various times defined in the SOA record of a zone and change them to fit your needs.

Regards

CyberIT · 09-24-2020, 06:04 PM

Quote:

Originally Posted by bathory

Take a look at the various times defined in the SOA record of a zone and change them to fit your needs.

Regards

Thank you for that. I believe they are all at the default of 3600seconds. It just seems that only this one domain is giving the slowness.

Thanks!