1
I've been working on a small project the past couple days and have hit a small wall.
This is what I have so far:
- Static IP from Comcast
- Registered Domain from Dynadot
- Local Arch Linux DNS box running named on internal Static IP 10.1.10.205
- Devices I want on my network point to my Local Arch DNS box for DNS and have their own internal static IPs (So one of my boxes at 10.1.10.206 asks 10.1.10.205 for DNS queries).
What I want is to be able to say "ssh computer1.4lambda.net" and have 4lambda.net resolve to my static IP, which my router forwards the request to be resolved at my local DNS.
Well it isn't working, so I am here!
At Dynadot, I have my domain DNS record updated with:
4lambda.net A 50.249.112.214
Is that correct? This should be routing any queries to example.com to 50.249.112.214 which will lead that query to my Comcast modem/router.
From there, do I need to do anything such as forward port 53 to my local DNS or do I just tell my router to use my local DNS?
I am sure my local one is working, when I run "ssh computer1.example.com" internally it does find the other computer and resolve. Removing computer1 from my local DNS causes it to fail, so I am under the assumption that at least that is correct. I still don't understand why I can't do "ssh computer1" from a local machine though. However that is not as important.
Thanks for any and all help!
1
For security reasons I am using example.com
- See here for what information to obfuscate in your answer. If this is a publicly registered domain name then what's the point of obfuscating the name? That's just making it harder for us to help you. - http://meta.serverfault.com/questions/963/what-information-should-i-include-or-obfuscate-in-my-posts – joeqwerty – 2014-07-16T15:03:04.550Point taken. Edited – rusty – 2014-07-16T16:32:05.110