The other day I was trying to RDC from my work laptop to work desktop using my PC's hostname but it could find the desktop. Later on I tried with my desktop's IP which worked. Both the time I was on premise and was connected to the network physically.
I could RDC every other computer in our network.
After my research, I checked firewall was disabled, flushed and re-registered dns etc. Everything seems to be in order. However, when I tried to do reverse DNS lookup it didnt work for my desktop.
After that my IT guy and I checked everything on the AD server and there was no entry for my hostname or the IP. So we manually added the dns record which didnt work either.
Following is the note from IT:
AD / DHCP on a server on a different subnet DNS on another server on
the above subnet
The Pc is on a VLAN again different subnet. The Cisco Switch controls
the VLAN but talks to DHCP server for scope
Even adding the A host on forward lookup manually can’t resolve using
hostname for ping / mstsc. Both work for IP so deff DNS issue.
Tried to ipconfig /release and renew after giving a different PC the
IP address that was originally assigned to this one thinking it would
force DNS to update.
There is no entry for the IP or the Hostname in DNS even when the IP
changed after a renew. The firewall on the PC is off. However there is
the entry in the DHCP address lease table.
Tried flushDNS and ReregisterDNS.
If anyone could point me to the right direction here I would be grateful. Also, if you need further information please let me know.
Thanks
This is not the correct forum for this question. However, I can point you in the right direction.
Your correct that this is a DNS issue (so it seems).
The entry that is missing is from the host you are trying to reach (not the client that your trying this from).
Make sure all of the systems are using the same DNS servers. Make sure the DHCP Client Service is running (even if IP address is hard coded) as that is what actually records the the host name and IP address in DNS.
It sounds like you have the routing set up or you would not be able to do it by IP address.
Is the DNS zone in AD set up to allow dynamic updates? Do you have the domain name being sent out via DHCP?
Windows will (but not always) try to find a host by DNS and will fall back to a broadcast for the PC name. This might be why it works from one VLAN, and not from another.
Related
I make a web site to my local. I set bindings local.com and www.local.com. I add hosts xml to
127.0.0.1 local.com
127.0.0.1 www.local.com
So, I can connet on my pc like
local.com,
www.local.com,
192.168.1.35
But another pc on my network can't conenct with friendly name
www.local.com,
local.com,
But same pc can connet with ip
192.168.1.35
How can that another pc connect with friendly name ?
IP Addresses are the numerical identification for each device on a computer network.
Named Addresses invented, because remembering each device Address's turned to a difficult job.
So someone must know's which names must be converted to which IP Address.
DNS Servers are responsible to do this translation. But you done that locally. Actually you don't have a DNS Server on your local System, So you can't tell to others that "WWW.Something.COM" is my Address.
If you didn't connected to the internet, you must establish a DNS Server or done this task manually in all clients:
https://helpdeskgeek.com/networking/edit-hosts-file/
Running a DNS Server is another task. you can search for DNS Server applications like https://simpledns.com/ or you can setup a DNS Server using Windows Server. for both scenarios you need to tell to your clients to add your DNS Server Address to their network Adapter settings.
or If you are connected to the Internet, you can Use a NoIP to register a free Address:
https://www.noip.com/
you then need to download an application (In Noip.com) to monitor IP changes, it will monitors your IP address and it changes and then tells to NOIP.com to translate your address into your current IP address.
Actually NOIP will registers your address globally around the Internet network and each one who can access to the internet is able to reach to your address.
I have a newly installed MikroTik switch, and have successfully configured it for VPN traffic. However, behind the switch is a Linux server to which I am unable to connect via PuTTY. I can see the server and its IP address in Winbox->IP->DHCP Server->Leases, but as I say, I can't connect from within the VPN. I've made several attempts to add a rule to the firewall that would permit access and I've even gone so far as to uncheck the firewall router box in Quick Set, but no matter what I've tried, it always times out. To be clear, I'd like the server to be visible to all machines connected to the switch - both via ethernet and via pp2p.
I've been googling for hours, and I'm completely new to network engineering, so any help would be greatly appreciated.
I think the problem may be due to NAT and your VPN IP Subnet. I have my VPN users in 192.168.4.0/24 the main subnet is 192.168.0.0/22. In Winbox got to IP>Firewall then in the NAT tab make sure you have a masquerade action on your VPN subnet. I think the VPN quick set adds one but if your using different subnets it gets confused. See the image for what I have set for my VPN users to access servers and resources on the main network.
I have a domain,
www.xyz.co.uk
now I would like to point for example,
www.data.xyz.co.uk to the ip address of my server(digitalocean)
So far what I did is, I have created a hostname on dns managementconsole of godaddy, with data.xyz.co.uk and pointed that to my ip address.
I am little confused wether that is it or I need to do more on my server ? Secondly when I do ping data.xzy.co.uk in terminal I get unknown host response.
Could somebody points me in right direction.
I manage to get the resolved the issue by adding A record in DNS settings of my hosts account and pointing that record to a desired Ip.
I'm working in a company,
When I log on to my pc under Domain X, when I open a browser and put a URL www.someUrl.com it get resolved.
In a cloud machine Y I'm developing on, it does not get resolved, and I was wondering if there is some way of knowing how the mapping is done.
What I've tried:
Taking the IP address I'm getting from pinging successfully in machine X and ping it in machine Y.
Googling --> Didn't find nothing, guess I'm not searching for the problem correctly.
Contact my IT department --> The are busy.
Any help would be appreciated.
I'm missing a few bits of information to fully determine the cause of this issue, but I can offer a few ideas/solutions:
When a host is under a domain, upon attempting to access a certain address by name, the host automatically attempts to resolve it both as entered and by adding the domain suffix to it (so someUrl.com will also be resolved as someUrl.com.domainName), so if, by any channce, this suffixed address is the real address, this could be the answer.
Another likely cause is the DNS server responsible for resolving your host's queries. If someUrl.com is not properly registered in global DNS servers and is only defined locally on your company's DNS, the cloud machine's DNS server will not be able to resolve the address.
One more option is that the domain is, in fact, resolved, but is not accessible from the cloud machine (either because of firewall configuration restricting the source of requests made to it, or because it is located behind the company's NAT, which your local machine does not have to go through to reach someUrl.com)
If none of these appear to be the cause of the problem, here's what you should do:
ipconfig /all on both machines, to see what DNS server they are configured with
nslookup someUrl.com from both machines, to see which DNS server answers the query
if only the local host gets a proper nslookup response, try nslookup from the cloud using the host's DNS server (nslookup someUrl.com <host DNS>)
ping the IP address of someUrl.com from both the host and the cloud (you said you performed this test, but you did not share the results :))
What it turned out to be eventually, was that the machine I was trying to resolve was in the organization's intranet, that's why it could not be accessed from machine Y in the cloud which is public.
We build a set of virtual appliances used throughout the company. The networking on the VM is set to NAT to prevent external DNS records from being created, unfortunately at least once a month someone switches it to bridged so other people can connect.
The problem with this is they all have the same hostname, as soon as the external DNS record is created everyone is routed to this new address causing issues until we track down the culprit and change it back to NAT or change the hostname.
Is there a method in a 2008 R2 AD environment to blacklist a hostname and prevent a DNS record from being created? DNS is configured so a record can be created by anyone with a network device which makes it messy. Adding an A record pointing to 127.0.0.1 won't work as people work with the VM from outside it with a client.
This is a multi-domain environment and the root domain has DNS restricted, if there's a way to force the VM to request a DNS record in that space that could work.
Edit: To clarify, the DNS record is created via DHCP
Create static host records for those required, then set the permissions to them to deny writes. That should prevent them from being updated.