Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
DNS A record not working as expected
See original GitHub issueHoping someone can help me out! Have tried ZEIT’s Twitter support but they were not able to help 😞
I have a domain registered with Now - tread.fyi. There is a static website hosted at the root of this domain https://tread.fyi/. And I have a Node.js server running in a DigitalOcean droplet.
I want to route requests for https://realtime.tread.fyi/ to the DO droplet. I have added an A record to Now’s DNS records, which can be verified here. But pinging the URL shows the requests are routed to alias.now.co instead of the droplet’s IP address.
→ ping https://realtime.tread.fyi
PING alias.zeit.co (3.9.28.56): 56 data bytes
Request timeout for icmp_seq 0
I’m guessing that the default CNAME/ALIAS records on Now’s DNS are intercepting the requests to my subdomain. Here are the DNS records:
ALIAS http://alias.zeit.co.
* CNAME http://alias.zeit.co.
realtime A 157.245.38.176
How can I solve this so that the subdomain correctly points to the droplet’s IP?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I had the same issue because I did this:
now dns add foo.com sub.foo.com A 1.2.3.4It works if I do:
now dns add foo.com sub A 1.2.3.4(Don’t include the main domain in the subdomain or you will end up with
sub.foo.com.foo.com)Closing this as both @jgillich and @RodolfoSilva have pointed out the correct answer and resources to answer this.