Link to home
Start Free TrialLog in
Avatar of detox1978
detox1978Flag for United Kingdom of Great Britain and Northern Ireland

asked on

Forward DNS zone

Hi All,

We have an internal and an external DNS server.  And I have been asked to setup forwarders on the internal DNS server, this has worked well.  However if it has a zone but no record it doesn't forward the request.

I get the following error when i try to forward zone it has records for;

The server forwarders cannot be updated.
The zone already exists.


What are my options.
Avatar of Brian Pierce
Brian Pierce
Flag of United Kingdom of Great Britain and Northern Ireland image

This is as expected - if the DNS server hosts a zone then it is said to be authoratitive for that zone and can issue either the IP or a 'not found' response to a DNS lookup request.

A forwarder will only be used if there is a request for a DNS lookup for a zone for which it is not the host.
Avatar of detox1978

ASKER

Is there a way around this?

An external company runs the external DNS server and every so often they will add new records to their server and not tell us.

All there records are public DNS, if that helps.
You should only have zones in your DNS for the domains that you have.

Use forwarders or conditional forwarders to point at external domains
is there a way to remove the SOA?

Maybe setup another DNS server and transfer the records?
I'm trying to figure out what your setup - can you explain a bit more?

You have a domain with a DNS server for your own domain - so where does the other zone come from ?
The have a head office that runs the DNS accessible to the internet.

There are 20+ local sites, each with there own DNS server.  At the moment when a new record is added to the head office DNS server I have to manually add it to our local DNS server.  I was hoping i could just setup DNS forwarding.
Head office runs a UNIX DNS server and the local sites each have their own setup as we don't swap data.
Im not sure I understand "DNS accessible to the internet" - publically accessable from the internet - not very secure!!!

Where you have miltiple sites you can simply have multiple AD Integrated DNS servers, the DNS will replicate automatically and no maintenence is required - this would be the preferred option.

Alternatively the DNS server on the main site can be configured to use zone transfers to update DNS data from itself to a secondary DNS server at the local site - this could be used if AD integrated DNS was not used.
ASKER CERTIFIED SOLUTION
Avatar of Brian Pierce
Brian Pierce
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
how does it work regarding overwriting their records.

e.g. local.mycompany.com needs to be 10.0.10.100 for us, but is a public IP on their server.
It doesn't - s secondary zone is a read-only zone - it can only be updated by the primary (in this case the unix), server
i can just use root hints to read there server.  or point at it directly.

I need to use ours then theirs.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
resolved using MS support