Running dnsmasq as an authoritative DNS server

5,793

Your NS record for h.lohray.com is currently as follows:

h.lohray.com.       1800    IN  NS  50.19.103.190.

Which is wrong. NS records should specify not an IP addresses, but domain names of a nameservers, like this:

h.lohray.com.       1800    IN  NS  h.lohray.com
h.lohray.com.       1800    IN  A   50.19.103.190.

or like this:

h.lohray.com.       1800    IN  NS  ns.h.lohray.com
ns.h.lohray.com.        1800    IN  A   50.19.103.190.

Your DNS server at 50.19.103.190 seems to work - it answers when I query of i7.h.lohray.com

Share:
5,793

Related videos on Youtube

Lord Loh.
Author by

Lord Loh.

...

Updated on September 18, 2022

Comments

  • Lord Loh.
    Lord Loh. almost 2 years

    I am trying to implement a dynamic dns service for my computers. I have pointed h.lohray.com to my EC2 instance in the NS record of lohray.com and have installed dnsmasq on that system and have made sure to unblock the firewall port.

    For now, I have statistically added an entry on my /etc/hosts file.

    129.118.19.163 i7.h.lohray.com

    however, i7.h.lohray.com does not resolve correctly with nslookup or dig :-( This is the only time I could have this resolved (online nslookup) - 50.19.103.190 is the IP address of the EC2 instance where dnsmasq is running. Where could I have gone wrong?

    • Lord Loh.
      Lord Loh. about 12 years
      The host i7 might be dead if my computer is off.
  • Lord Loh.
    Lord Loh. about 12 years
    I set the NS record for h.lohray.com to 50.19.103.190
  • johnshen64
    johnshen64 about 12 years
    i tried web dig, and here is the result for the authoritative dns server which i have added to my answer. it seems that the dns server is indeed set up, so it has to be something within you instance or ec2.
  • johnshen64
    johnshen64 about 12 years
    good news i have succeeded resolving it now. must be dns propagation. so it will take ttl time to propagate throughout internet (unless the dns servers that ignore ttl and cache records for longer). looks like your setup is correct. must be some sort of delay when i tested previously. sorry about that.
  • Lord Loh.
    Lord Loh. about 12 years
    Unfortunately, I still get i7.h.lohray.com IN NS 50.19.103.190 1800s (30m). I am expecting a different IP for i7.h.lohray.com. 50.19.103.190 is not the ip I set for i7.h.lohray.com in the hosts file :-(
  • Sandman4
    Sandman4 about 12 years
    Until you will read my answer, I can't help.
  • Lord Loh.
    Lord Loh. about 12 years
    Oh! I am sorry :-(. I think I read whatever was on my mind than what was on the screen :-( My shortcoming. When I query 50.19.103.190 for i7.h.lohray.com, I get the right IP. I am still to figure out how to get the dnsmasq to resolve right. - Thank you.
  • Sandman4
    Sandman4 about 12 years
    Ughm, you still seem to read whatever it is on your mind :). DNSMASQ DOES RESOLVE RIGHT. Your DNS server at 50.19.103.190 works OK.
  • Sandman4
    Sandman4 about 12 years
    The "bad" record resides on nsX.hostindia.net, which is probably your DNS hosting or registrar.