![]() This will tell you the path that computers outside of the network are taking to attempt to get to your server. You'll want a reverse record pointing 96.x.x.x to and ns.Ī side note: it is highly inadvisable to host public DNS on a single server in a single location with non-redundant power and internet and routers and a consumer-grade connection.Īlso, from outside of the network, run traceroute -p X ns. where X is a port number DNS uses, for each port number DNS is using. Just a quick thought: It's possible you may also need a reverse record, sometimes called a PTR record. First, we strongly recommend you connect the server to your router using an Ethernet cable while you can use Wi-Fi, Ethernet offers faster performance and a more stable connection. If it were a router issue I would be able to find out the 96.x.x.x address but a traceroute would fail at the router.Ĭheck this link out: It uses a bunch of fancy confusing language but basically what you're missing is that glue record.Īs you can see from the diagram, there's an infinite loop going 2->3->4->5->4->5->4->5->4 Since I'm unable to get the IP address of ns.invatamax.ro at all, it is not a router issue. When did you have your domain provider set up the pointer? If it was within the last day, it needs time to replicate around the world. My computer attempts to resolve invatamax.ro, recognizes that you've set up the nameserver to be ns.invatamax.ro, but then it is unable to resolve what IP address (the 96.x.x.x address) it should look to. it looks like your top level domain provider hasn't properly pointed ns.invatamax.ro to 96.x.x.x. it's as if the airport extreme which "holds" the exterior 94.x.x.x address doesn't pass DNS along to my 10.0.1.3 ns server. From a any computer in my network I CAN see my ns and everything works. NOW: Nobody seems to be able to access my ns. to resolve any of my records. The dot on the server will turn the color green from the color red Now, expand the server and expand IPv4 entry to click on the General node. I've already added my 96.x.x.x to point ns. with my registrar as attached. My dns server has an A record pointing to ns. and a PTR doing the reverse. Mac mini server always gets a reserved DHCP IP from the Airport Express:ġ0.0.1.1 as the dns (this ip is the airport express itself) The mac mini will host my domain .ĩ6.x.x.x as the external static IP from the ISP The Mac mini server is connected to one of the ethernet ports. The WAN connection (static IP and ISP nameservers) goes into the wan port of the Airport Extreme. The setup can be expensive If you want a compatible device, you can find many options for home VPN routers. However, this configuration process is less straightforward and often restricted on routers. I have a Mac mini server i want to setup to host a couple of things. With VPN apps installed on individual devices, you can easily switch between servers. ![]()
0 Comments
Leave a Reply. |