One domain is not working, the other is working perfectly. What's the problem?

October 18, 2019 197 views
DigitalOcean Apache Django

I have setup two domain names with digitalocean, both are set up the same way. One domain, ablundberg.com, is working just fine. The other one, lundbergandassociates.com, cannot resolve and this is after five days. Is there something I have messed up and need to change or what should I do?
I am using Apache with lundbergandassociates.com being the ServerName and ablundberg.com is a ServerAlias. The website is run with Django and both are added to Allowed_hosts. Their A names are also the exact same.

2 comments
  • Please post nginx’s configs and DNS records

  • A

    ablundberg.com
    104.248.42.17

    3600
    NS

    ablundberg.com
    ns1.digitalocean.com
    1800
    … with 2 more NS records.
    A

    lundbergandassociates.com
    104.248.42.17
    3600
    NS

    lundbergandassociates.com
    ns1.digitalocean.com
    1800
    … with 2 more NS records.
    I’m not using nginx of what I’m aware.

1 Answer

Hi @DavidWithRemovedLastname,

The issue doesn’t seem to be your droplet but with your DNS. From what you’ve provide us with I can’t make sense where exactly is the problem so I’ll tell you the solution.

For your domain lundbergandassociates.com go to your Control Panel and make sure to create two records. The first one would be an A record :

Hostname     Will Redirect To     TTL
@            Your Droplet's IP    800

The second record would be for your wwww.lundbergandassociates.com, this time, it would be a CNAME record

Hostname    Is An Alias of                TTL
wwww         lundbergandassociates.com    800

Once you’ve done this, your issue should be resolved.

Regards,
KDSys

  • Hi KDSys,

    Thanks for the answer! I updated the DNS records and they currently look like this:

    CNAME

    www.lundbergandassociates.com
    is an alias of
    lundbergandassociates.com.
    800
    A

    lundbergandassociates.com
    directs to
    104.248.42.17
    800

    NS

    lundbergandassociates.com
    directs to
    ns1.digitalocean.com.
    1800

    NS

    lundbergandassociates.com
    directs to
    ns2.digitalocean.com.
    1800

    NS

    lundbergandassociates.com
    directs to
    ns3.digitalocean.com.
    1800

    Sadly, I do not see a different result than I did before. Maybe I missed something

    Thanks in advance!
    Kind regards
    David

    • Hi @DavidWithRemovedLastname,

      Now when I dig your DNS records at the Digital Ocean’s Nameservers, I can see the records are there.

      I’ll recommend you to wait a bit and see if the DNS will start propagating. This process can take up to 24 hours. If this continues, I’ll recommend contacting your registrar to see if there are any blocks placed on the Domain. Everything else seems to be configured properly.

      • Hi again @KDSys,
        I much appreciate the help you are giving!
        I am, however, sad to say that the issue has not been resolved and I spoke with the people over at my domain registrar and they saw nothing that they could help with and told me to turn back here.
        Is there anything else you can think of that might make the differance ?
        Kind regards
        David

        • Hi @DavidWithRemovedLastname,

          I just pinged your domain and I can see it’s resolving

          ping lundbergandassociates.com
          PING lundbergandassociates.com (104.248.42.17) 56(84) bytes of data.
          64 bytes from 104.248.42.17 (104.248.42.17): icmp_seq=1 ttl=54 time=35.5 ms
          64 bytes from 104.248.42.17 (104.248.42.17): icmp_seq=2 ttl=54 time=38.4 ms
          ^C
          --- lundbergandassociates.com ping statistics ---
          2 packets transmitted, 2 received, 0% packet loss, time 1001ms
          rtt min/avg/max/mdev = 35.563/36.995/38.428/1.445 ms
          

          Can you share what was the root cause of the problem?

          Regards,
          KDSys

          • Hi again @KDSys,
            I have had time to speak with people about the problem, including the Digitalocean support team who have been very helpful, and what seems to happen is that the domain is resolving in some parts of the world but not others. Sadly where it need to resolve it isn’t.
            When I ping the domain this is the result I get:

            ping lundbergandassociates.com
            ping: cannot resolve lundbergandassociates.com: Unknown host

            and what someone at the digitalocean support team found, I don’t know if they want to be named so I won’t, that the places where the NS records don’t resolve match up to the places where the A records don’t. Which they thought would indicate that there is a problem with the NS records. So I have tried to re-add them but sadly with no luck.

            Kind regards
            David

Have another answer? Share your knowledge.