Hi to whoever reads this, I set up a simple A record for the subdomain remark42.mathiasfuchs.de in order to set up a small commenting system, redirecting to my IP 139.59.201.231 (same as the domain mathiasfuchs.de has always been directing to) but even after waiting for a few days, nameservers don’t seem to know about the subdomain remark42.mathiasfuchs.de. I expected to be able to
ping remark42.mathiasfuchs.de
it, but to no avail. Thanks for help, Mathias
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hi there @matthew887mm,
It looks like that your DNS is not managed via DigitalOcean because your NameServers are currently set to:
Name Server: ns1.routing.net
Name Server: ns2.routing.net
Name Server: ns3.routing.net
You can check that via this website:
This means that you need to add all of your DNS changes via your DNS provider.
Another option would be to go to your Domain name provider and change your nameservers to the DigitalOcean nameservers. That way you will be able to manage your DNS zone via DigitalOcean directly.
Basically, the nameservers specified under your domain name provider, ‘tell’ your domain name which DNS zone to use.
Hope that this helps. Regards, Bobby
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.