3

I have an internal DNS server. I've added a custom record for a domain name that is public. I want to add local records but keep the public domain name resolved. For instance : foo.bar.com = wan ip -> SAT -> local server

I've added a zone bar.com and a custom record : gum.bar.com = lan ip -> local server

BUT I need to delegate other records, that means foo.bar.com should be left to the public DNS server. I saw the delegation option for a zone, I put my IPS DNS server, it works nice for a specific zone, like foo.bar must be resolved by the isp 's DNS. Now If I want to delegate a wildcart, it ain't work. You get I want to override the DNS server : resolve local names (the one you have records for) but other domain names mut be resolved by another server.

How can I achieve that, using a wildcard for a given zone ? Thanks mates

Improve this question

1 Answer 1

Reset to default
6

Delete your "bar.com" zone from your W2K3 DNS server. Create a zone "gum.bar.com", and create a blank host record in that zone pointing to the LAN IP of the local server. Problem solved. >smile<

The W2K3 DNS server can't be simultaneously authoritative for a domain while forwarding queries that it can't resolve to another DNS server. It's just a limitation of the product. Working around it, per the above, is how we've always handled it.

Improve this answer
8
  • Note that with this method, referencing the server by FQDN will be: server.gum.bar.com Commented Sep 15, 2009 at 13:28
  • 1
    This "limitation" is also in many other name servers. So, the solution of a subdomain is certainly the right one. Commented Sep 15, 2009 at 13:49
  • I don't think it's as much a limitation of any specific product as it is a limitation of the DNS protocol. Commented Sep 15, 2009 at 15:17
  • 1
    @joeqwerty: You don't have to specify a hostname-- you can refer to the zone's name itself-- gum.bar.com-- in the A record (an "@" record, in BIND terminology). Commented Sep 15, 2009 at 20:29
  • @Evan: I'm not sure what you're saying, but I mean that the FQDN of the server will be server.gum.bar.com and not server.bar.com. Can you elaborate on your comment? Thanks. Commented Sep 16, 2009 at 1:31

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.