Cannot resolve my domain name.

[Sir Asvald]

Hello guys. So I'm facing a problem where I cannot connect to my server by writing the fully qualified domain name of my server. Which is hq-dc1.learntotech.co.uk. I can ping and get a response by pinging the server's name.

 

 

This is the ping:

 

 

Also my Sophos UTM

 

 

 

 

[dalekphalm]

25 minutes ago, Abdul201588 said:

Hello guys. So I'm facing a problem where I cannot connect to my server by writing the fully qualified domain name of my server. Which is hq-dc1.learntotech.co.uk. I can ping and get a response by pinging the server's name.

 

 

This is the ping:

 

 

Also my Sophos UTM

 

 

 

 

I have a couple questions:

1. learntotech.co.uk - is that a real website on the web? If so, I assume you own the Domain Name?

2. Is the server located locally or externally (in a data center or something)?

[Sir Asvald]

6 minutes ago, dalekphalm said:

I have a couple questions:

1. learntotech.co.uk - is that a real website on the web? If so, I assume you own the Domain Name?

2. Is the server located locally or externally (in a data center or something)?

I got it working.  I just unplugged the Ethernet cable and plugged it in again.  

 

I own the domain, no site currently set up. Server is right next to me.

 

 

[U.Ho]

This is what we at work call "not a network issue" or a "server problem" since the server is responding to ping.

 

Glad you got it working though.

[Sir Asvald]

15 minutes ago, U.Ho said:

This is what we at work call "not a network issue" or a "server problem" since the server is responding to ping.

 

Glad you got it working though.

Well, I couldn't access the entire directory

 

[U.Ho]

2 hours ago, Abdul201588 said:

Well, I couldn't access the entire directory

 

Yea, I get it.

 

Thing is, the network connection was still fine since ping did resolve the DNS record and ping was fine.

This is pretty much just semantics though, and don't really matter when it comes to a forum discussion. I just get this alot at work and it seemed like a good idea to get that straight. 

 

Like I said, glad there's no issue anymore.

 

 

[Sir Asvald]

9 hours ago, U.Ho said:

Yea, I get it.

 

Thing is, the network connection was still fine since ping did resolve the DNS record and ping was fine.

This is pretty much just semantics though, and don't really matter when it comes to a forum discussion. I just get this alot at work and it seemed like a good idea to get that straight. 

 

Like I said, glad there's no issue anymore.

 

 

Also, there wasn't an A record in the DNS for the server.

[U.Ho]

1 hour ago, Abdul201588 said:

Also, there wasn't an A record in the DNS for the server.

Huh?

 

Then that's weird.

 

How did ping resolve address if there was no DNS record?

 

Seriously, if you know, please do tell because that's not what it looks like in the screenshots.

 

What you show in the screenshots is

1. you pinging a FQDN which gets resolved into an IP, ping times out.

2. You pinging a short address which gets resolved into a FQDN, which in turn gets resolved into an IP, ping times out.

 

Now, is 92.242.132.15 the correct IP address for your server?

If it is, then again, this is not a DNS issue.

How did you check that there was no DNS record?

Do you run the server yourself?

 

What I got wrong at first was that the server would respond. It actually doesn't even respond to the pings in the screenshots.

[Sir Asvald]

 

3 minutes ago, U.Ho said:

Huh?

 

Then that's weird.

 

How did ping resolve address if there was no DNS record?

 

Seriously, if you know, please do tell because that's not what it looks like in the screenshots.

 

What you show in the screenshots is

1. you pinging a FQDN which gets resolved into an IP, ping times out.

2. You pinging a short address which gets resolved into a FQDN, which in turn gets resolved into an IP, ping times out.

 

Now, is 92.242.132.15 the correct IP address for your server?

If it is, then again, this is not a DNS issue.

How did you check that there was no DNS record?

Do you run the server yourself?

 

What I got wrong at first was that the server would respond. It actually doesn't even respond to the pings in the screenshots.

The Server has 2 Ethernet ports. Two seperate networks. One on the 192.16.1.x and 172.16.105.x.

The 192.16.1.x is on the "public" and the 172.16.105 is the "private". I've set it up as a NAT server. 

 

[U.Ho]

13 minutes ago, Abdul201588 said:

 

The Server has 2 Ethernet ports. Two seperate networks. One on the 192.16.1.x and 172.16.105.x.

The 192.16.1.x is on the "public" and the 172.16.105 is the "private". I've set it up as a NAT server. 

 

Ok. That's good.

 

So the 192.16(8?).1.x is NATted to the internet while you should access the server via 172.16.105.x?

 

Now, the FQDN resolved to 92.242.132.15 which is probably your public IP, and whatever the public IP hits in your network didn't respond to ping.

 

If you mean you didn't have a DNS record for the server on your personal DNS server that should resolve the FQDN to 172.16.105.x, then I do understand. It didn't find the record there so it went on to find it in public DNS, and found it too.

 

Is it now resolving to 172.16.105.x after adding the record?

[Sir Asvald]

12 minutes ago, U.Ho said:

Ok. That's good.

 

So the 192.16(8?).1.x is NATted to the internet while you should access the server via 172.16.105.x?

 

Now, the FQDN resolved to 92.242.132.15 which is probably your public IP, and whatever the public IP hits in your network didn't respond to ping.

 

If you mean you didn't have a DNS record for the server on your personal DNS server that should resolve the FQDN to 172.16.105.x, then I do understand. It didn't find the record there so it went on to find it in public DNS, and found it too.

 

Is it now resolving to 172.16.105.x after adding the record?

Yes. Although the 92.242.135.15 is not my IP. It's http://barefruit.co.uk/ resolver. Also, I can resolve both IPs of my server.