#1
  1. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    May 2013
    Posts
    5
    Rep Power
    0

    Finding the DNS server for a subdomain


    Hello, I am pretty new to DNS, so please bear with me. My company asked me to move web services and email to another provider. I set up the other provider and changed the name server pointers in Network Solutions. All went well. Now I find they have a subdomain that points to a different IP address. The subdomain, xxx.domain.com is still resolving to the specific address. So I am not sure where and how this subdomain address is being resolved. Is there a tool for determining where the resolution is taking place?
  2. #2
  3. Did you steal it?
    Devshed Supreme Being (6500+ posts)

    Join Date
    Mar 2007
    Location
    Washington, USA
    Posts
    13,961
    Rep Power
    9397
    Can you tell us the domain? Are you sure you've got the new provider working? Are your DNS lookups cached?
  4. #3
  5. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    May 2013
    Posts
    5
    Rep Power
    0
    Originally Posted by requinix
    Can you tell us the domain? Are you sure you've got the new provider working? Are your DNS lookups cached?

    The domain is computerguysmt.com. The subdomain is owa.computerguysmt.com. When I ping the two, they resolve to different addresses. I moved the computerguysmt.com domain last Saturday, so I believe the change has propagated. I am hosting with Justhost. Network Solutions points to the JustHost name servers. There is nothing in the DNS entries on Justhost for owa.computerguysmt.com. I have moved to a different PC at a different site that never accessed either entry, so I do not believe there is any caching involved.
  6. #4
  7. Did you steal it?
    Devshed Supreme Being (6500+ posts)

    Join Date
    Mar 2007
    Location
    Washington, USA
    Posts
    13,961
    Rep Power
    9397
    For me, computerguysmt.com resolves to 173.254.28.59 with nameservers ns1/2.justhost.com.

    As far as I can see owa.computerguysmt.com doesn't exist. You say you're pinging it and not doing an address lookup... What do you get? Your ISP/DNS provider might be trying to send you to a search page, like OpenDNS will resolve non-existant hostnames to 67.215.65.132 (hit-nxdomain.opendns.com)
  8. #5
  9. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    May 2013
    Posts
    5
    Rep Power
    0
    Well, I did start off by saying that I was pretty new to DNS. You are right. My provider, Cox, has resolved the subdomain to a different IP address. I knew if I tried to access the web page, they would re-direct that, but I was not aware they would redirect a ping. So I did break the subdomain pointer in the move. As I understand it all I have to do now is add an A record to the JustHost DNS for this subdomain. Thank you for your assistance.
  10. #6
  11. Did you steal it?
    Devshed Supreme Being (6500+ posts)

    Join Date
    Mar 2007
    Location
    Washington, USA
    Posts
    13,961
    Rep Power
    9397
    ping and nslookup (what I was using) do two different things. With ping you'll get results more or less like how a browser might deal with it, but with nslookup you'll get raw information without any ISP trickiness.

    From Windows,
    Code:
    C:\>nslookup owa.computerguysmt.com. 8.8.8.8
    Server:  google-public-dns-a.google.com
    Address:  8.8.8.8
    
    *** google-public-dns-a.google.com can't find owa.computerguysmt.com.: Non-existent domain
    
    C:\>ping owa.computerguysmt.com.
    
    Pinging owa.computerguysmt.com [67.215.65.132] with 32 bytes of data:
    Reply from 67.215.65.132: bytes=32 time=39ms TTL=55
    Reply from 67.215.65.132: bytes=32 time=46ms TTL=55
    Reply from 67.215.65.132: bytes=32 time=36ms TTL=55
    Reply from 67.215.65.132: bytes=32 time=60ms TTL=55
    
    Ping statistics for 67.215.65.132:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 36ms, Maximum = 60ms, Average = 45ms
    
    C:\>nslookup 67.215.65.132 8.8.8.8
    Server:  google-public-dns-a.google.com
    Address:  8.8.8.8
    
    Name:    hit-nxdomain.opendns.com
    Address:  67.215.65.132
    Then I recognized hit-nxdomain.opendns.com as a search page thing I mentioned.

    Also,
    Code:
    C:\>nslookup -type=all computerguysmt.com. 8.8.8.8
    Server:  google-public-dns-a.google.com
    Address:  8.8.8.8
    
    Non-authoritative answer:
    computerguysmt.com      internet address = 173.254.28.59
    computerguysmt.com      nameserver = ns2.justhost.com
    computerguysmt.com
            primary name server = ns1.justhost.com
            responsible mail addr = root.just59.justhost.com
            serial  = 2013052308
            refresh = 86400 (1 day)
            retry   = 7200 (2 hours)
            expire  = 3600000 (41 days 16 hours)
            default TTL = 300 (5 mins)
    computerguysmt.com      MX preference = 0, mail exchanger = mail.computerguysmt.com
    computerguysmt.com      text =
    
            "v=spf1 a mx ptr include:justhost.com ?all"
    computerguysmt.com      nameserver = ns1.justhost.com
    (The trailing period for "computerguysmt.com." means to use that literal name without trying to look inside my network for it first.)
  12. #7
  13. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    May 2013
    Posts
    5
    Rep Power
    0
    In my case, nslookup was tricked by the ISP and returned the same address the ping did. The response was a few lines shorter.
  14. #8
  15. Did you steal it?
    Devshed Supreme Being (6500+ posts)

    Join Date
    Mar 2007
    Location
    Washington, USA
    Posts
    13,961
    Rep Power
    9397
    You can also use a different DNS server - the second argument to nslookup. Try 8.8.8.8 or 8.8.4.4, Google's public servers.
  16. #9
  17. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    May 2013
    Posts
    5
    Rep Power
    0
    Thank you for the advice. I made the change and now I am seeing what is really happening. Both ping and nslookup did not resolve the owa subdomain.

IMN logo majestic logo threadwatch logo seochat tools logo