I want to identify the Public IP address of a local company. More specific, i need the IP address where the offices are located. Because it's a small company, i assume they only have 1 public IP. The only thing i had, was the domain name. But i already did some investigation in DNS based on that domain name.
Result of the investigation based on domain name:
The company has 1 website, hosted by a hosting company. In DNS i did a lookup and i fetched the IP address of the website (A record), but it's the IP of the hosting company.
I found the domain name and IP address of 2 DNS servers registered for the domain, but they both are DNS servers of the hosting company which hosts the domain (NS records).
I found the domain name and IP address for 1 mail server registered for the domain (MX record). it seems that the company uses outlook as a mail server because the (MX record) is: domainname.com01c.mail.protection.outlook.com.
As you can see the results i already got are useless because they all point to services that are not hosted in the company's local offices but elsewhere.
Is there another way or method that i can use to identify the public IP used from the company's local offices? Or can i do more investigation based on the results i already found in DNS?
Use their Domain name to do a Whois Lookup:
https://whois.domaintools.com/
For example, with Google:
https://whois.domaintools.com/google.co.uk
You can also Use Maltego for more in-depth information on this but this is probably a question for https://security.stackexchange.com/
Maltego: https://www.paterva.com/web7/
Related
I have a domain that I bought in wix, Now I want to host my website in DIgital Ocean, How to connect droplet to wix domain
Yes.
Wix will probably use its name servers to ensure your domain's records are published. Wix provides a mechanism to manage your domain's records. You are able to add e.g. A, CNAME, TXT records.
See: Adding DNS records in your Wix account.
Droplets will generally be published on the Internet using IP(v4) addresses. You will want to add A(ddress) DNS records to alias your chosen host name in your domain to the Droplet's IPv4 address. For exmaple, to reference your droplet as droplet.[your-domain-name], you would create an A record with host name droplet with value set to the droplet's IP address.
Apps are published using SOMETHING.ondigitalocean.app (DNS) name. You will want to add CNAME DNS records to alias your chosen host name in your domain to the App's DNS name. For example, to reference your DigitalOcean Apps as app.[your-domain-name], you would create a CNAME record with host name app with value set to the app's SOMETHING.ondigitalocean.app name.
Hi Our site is based on Smartphone, Laptop, Gadgets Specs, Price
and we are using Linode server to get host our site but same sit opening in Linode rDNS, due to this most of our links such as https://www.pdevice.com/product/samsung-galaxy-s20-ultra-5g-price-specs opening with Linode domain address, we also contacted to them they have told us that, It looks like "pdevice.com" is your domain name but since it's pointing to CloudFlare's IP, you would need a work around in regards to setting reverse DNS. An option would be to create a subdomain and point this to your server's IP address. You may be able to get around this by having the "www" record for your domain point to your server's IP addresses rather than Cloudflare's IP addresses. and as we told we are using Cloudflare to provide CDN and DNS so how to solve this isse we can't recognize, because it shows issue while past RDNS to Subdomain.pdevice dot com, so how to do this with our server.
I'm very confused by the fundamentals of DNS records (in this case MX records). Right now I have registered a domain name (let's call it example.com). This domain is configured to my linode's IP via their nameservers.
The default MX record that is in the Domain Manager is 'mail.example.com'. Fair enough.
I followed this tutorial about setting up a exim server.
Exim Tutorial in Linode Library
and I'm kind of confused. My default hostname on the machine is 'antares' and thus the FQDN is 'antares.example.com'. In this tutorial I don't see how this 'mail.example.com' is coming into play? Where do I specify this? Or should I point the mail MX record to antares.example.com?
I'm very new to DNS records and even more new to mail records. Any hints to clarify my misunderstanding would be invaluable.
the DNS server for your domain will by default serve up the www or .domain.com entry to web browsers etc but it actually hosts a bunch of name pointers for other services, one of which is mail exchange.
Services which need your mx record value know how to look it up from your DNS server, so in this case they will find mail.domain.com when you supply the domain.com part.
If you need to set up a mail server you will need to change the mx record in your domain manager to point to your machine ip, this can be different from your default www host name/ip on the same domain as every service can be served by a different host (any ip).
I need a IM client that support yahoo and allow user to set yahoo IM server address.
Yahoo IM servers names (scs.msg.yahoo.com, scsa.msg.yahoo.com, scsb.msg.yahoo.com, scsc.msg.yahoo.com) are not accesible through my company LAN, so I should use IP addresses of their servers.
We can find ip of a domain name by simply pinging that domain name.
My problem was related to another network issue (port 443 was blocked) but initially I supposed that it relates to server ip address.
How is it possible to access an internal resource (email server / FTP server) using its external IP address but from within the network ?
The situation is that a number of users have laptops and work out of the office several days per week. I don't want them to have to change the connection details from 217.x.x.x to 10.0.0.x every time they come into the office, then back again when they leave.
I have external access working, so they can connect using the 217.x.x.x IP when on the road, but it doesn't work when they are in the office.
We have a router providing NAT access to the net and different servers for FTP, email etc.
This is what DNS is for - your external DNS provides the 217.x.x.x address for the names, while your internal DNS returns the 10.0.0.x IP address. Clients access resources by hostname, not IP address, and it's done.
Unless you have filters forbidding access to the external NAT'ed address from internal clients, I do not see why it should not work.