Master Server OS DNS settings

The dns server in /etc/resolv.conf should be the server itself.

The server should be a recursive server and in that case will be able to look up any domain as long as you set the root hints correctly.

So in resolv.conf it should have its own IP address? If that is correct, should it have the slave's address also?

Also I am not sure what root hints are.

tk

Thanks guys. Well, waiting on another issue. I realized I had to run this server at the same time as my current master until I I could cut the current master off. So, as I understand it you can only have one Master for the domain so I am setting the new one as a slave until I can make the switch. It doesn't resolve anything at this time even though the zones appear to be transferred from the current master. But, this new one is not registered yet. Also to add to the problem, I can't access the registrar site for various reasons yet so I am thinking that until I get that resolved and the new dns registered it will not resolve correctly. The server when set for the master as primary dns can resolve but when my laptop is set to use it for dns cannot. I assume that the registration is the issue. Once that is cleared up and I can see whats up, I will award the points or ask more if it still doesn't work.

tk

Unfortunately I don't have a choice on changing the IP address. It's currently remote so outside our allotted IP space and that account is going away. So I have to move it inside. My thought was let the new one, NS1, slave to the current master, NS. Then move everything to use NS1 in place of NS. Once they are moved then shut down the NS and reconfig the "new" master, NS1 from from slave. I'm using webmin so that should be easy. After the comments above and the pointers, I realized I was trying to create two masters for the same domains. So I decided to do it this way.

As far as resolv.conf on NS1, it has NS and NS3 in there and it will resolve when I ping different domains such as google from it. It just doesn't do anything when I try to use it as a DNS. That was why I thought it was a registration issue.

tk

Found part of the issue I think. I had to put in an allow-query and acl for my domain. Now it resolves for me. Not sure that is correct for an ISP though, to restrict queries to my domain. Don't others need to query for things like PTR?

tk

Since I am the ISP I assume that is all. So here is what I have in options with some edits to protect the innocent of course;


options {
      listen-on-v6 port 53 { ::1; };
      directory       "/var/named";
      dump-file       "/var/named/data/cache_dump.db";
        statistics-file "/var/named/data/named_stats.txt";
        memstatistics-file "/var/named/data/named_mem_stats.txt";

      dnssec-enable yes;
      dnssec-validation yes;
      dnssec-lookaside auto;

      /* Path to ISC DLV key */
      bindkeys-file "/etc/named.iscdlv.key";

      managed-keys-directory "/var/named/dynamic";
      allow-recursion {
            my-domain.net;
            };
      allow-transfer {
            xx.xx.xxx.xxx;
            };
      allow-query {
            any;
            };
};

the my-domain.net acl contains my /20 IP space.
Allow transfer right now is the master DNS IP address since this one is set to slave right now. Later this will be master and I'm not sure what to do with that. The only upstreams I will have then are the roots.

tk

I haven't dug into a config file for a DNS server for quite some time, but it appears to be correct.

I am going to resolve this. At this point I have tested it running as a master even with the other one still there and it works either as a master or a slave.

Thanks for the help!

tk