To resume the situation : I'm trying to use a new set of failover ip on my email serveur, after seting up the DNS, but the software I use on my email serveur (SmarterMail) doesn't see them. Why that ?
This is the complete situation :
I have a domaine name "ept.com" having a "A DNS record" to the physical IP machine.
mail1.ept.com has its A record to IP Failover IPA1
mail2.ept.com has its A record to IP Failover IPA2
mail3.ept.com has its A record to IP Failover IPA3
My goal : change IPA1, IPA2, IPA3 with IPB1, IPB2, IPB3
So I bought those new IP on OVH and set up the DNS :
mail1.ept.com has its A record to IP Failover IPB1
mail2.ept.com has its A record to IP Failover IPB2
mail3.ept.com has its A record to IP Failover IPB3
Propagation is complete. Then I setup reverse DNS. All is good so far.
The problem : Smartermail (software installed on the server) is supposed to list all the ip attached to the physical machine but all I can see is the old IP, not the new ones. So I am unable to tell him to use the "mail1.ept.com" smtp serveur with IPB1, "mail2.ept.com" with IPB2 etc
My question : Why does smartermail not see the new failover IP ? Is it matter of time ? (I setup the DNS 5 hours ago) My serveur is a Window Server 2016 Standard, should I do something window-specific ?
I am a beginner with that stuf, so I hope I've explained well... Thanks for your help !
I've found the solution.
I needed to go in Ethernet connection's properties, click on "Internet Protocol V4" and then the Properties button.
In the window that pops up, I clicked on the "advanced" button.
In this last window I could add the new IPs in order to be pulled by Smartermail.
Related
I'm banging my head against the wall at the moment.
What am I doing wrong here?
Your help would be much appreciated!
I started with AWS, bought a domain with route 53 and thought I could easily start using it.
Have made an A record with the server IP [static IP].
This seems to result in a DNS_PROBE_FINISHED_NXDOMAIN domain that can't be reached.
Even after waiting for hours.
Next solution I found on the web was setting a CNAME record;
This doesn't seem to work either.
What am I doing wrong here, any suggestions?
Thank you for your input
I have been learning a lot about AWS and it's quite handy.
[update]
* I found the dns name at the elastic IP settings [public DNS]
Step to do this :
Create A record of domain
Give same EC2 IP to A record
Change Security group of EC2 for port 80 and 443( if using) to all
Also try to ping EC2 IP by opening ssh port.
If do this all carefully. Then for IP changes sometime take times.
To see whether changes reflected or not.
Ubuntu :
open : /etc/hosts file and record for this.
terminal > sudo nano /etc/hosts/
add entry this file
xx.xxx.xxx.xxx www.xample.com
and save and close
then try to ping your domain and hit from browser. if this works then revert file changes. wait for Route53 to reflect changes in A record.
I found the problem.
When you register the domain, Amazon has set the nameservers, these nameservers on the register page and route53 were different. This is why I couldn't point the domain to my IP.
After setting them the same; the domain was pointing to my server.
I have recently brought a static ip address from my isp and i have a old computer to which i want to make my website live on internet i have read couple of forums and done research from it and nowhere i am to follow that.
I have a D-link modem and linksys router wrtg54 my isp have set up the static ip on d-link modem now i am confused what to do with the static ip as per my research many static ip are written on networks ip address,subnet,gateway and dns. I dont know how to set this up.
I had setup a static ip on my server computer which is 192.168.192.103 now i dont know what to do.Just for your refrence my Linksys router is configured on DHCP network.
I would really appreciate if someone can guide me or help me with a name who can setup this network thing so i can find the help for this problem.
Just to clarify, having a static IP does not resolve all the points for setting up a website, open to the public.
Consider the following points:
Do you have a webserver running on your computer?
(see www[.]apachefriends.org/de/index.html for windows or help[.]ubuntu.com/lts/serverguide/httpd.html for Ubuntu)
Does your ISP allow access on port 80?
(this would change to 443 if you use https)
Set the port forwarding on your router to the local machine
(http://portforward.com/english/routers/port_forwarding/Linksys/WRT54G/HTTP.htm for more info)
Get a domain (www.example.com) for your website
(If you registered already a domain, you have to change the target IP to your fixed IP which you received from your ISP)
Try to work this through and don't stop asking!
BTW!! I am able to connect to the internet via GNS3 Router. My question is about the IP Address that's assigned to the router!
Here it goes:
So this is my set up in GNS3:
Router 1 ---> Cloud (using my local MS loopback interface)
I had been struggling to get my router to the internet for a while. I'd run ipconfig and found that my wireless connection had an IP of 10.x.x.x with a gateway of .1. So obviously, I was trying to manually assign my MS loopback a random address of like 10.x.x.25 (/24, so still within the same subnet). But it never worked!!
Finally gave up, and then a new idea hit me. I set my MS loopback as "receive IP via DHCP", and also my GNS3 router interface that's facing the loopback cloud as "receive IP via DHCP".
They both received an IP Address of 192.168.x.x, and it connected to the internet as well. Duh.. no wonder my manual 10.x.x.x didn't work.
I did an ipconfig/all.... I just could not see a 192.168.x.x subnet in there at all.. no trace of it, just 10.x.x.x was present.
Where DID this 192.168.x.x IP come from? Difference between 10.x and the 192.x address?
Any help would be appreciated!
Nevermind, I think I figured it out. 10.x would be an IP address if it was handed out by my home router.
Here, since I allowed my Loopback to link up with my real router, my PC is behaving as a DHCP server instead, on behalf of my real home router. So 192.168.x is a pool belonging to my PC which handed out an IP to my virtual GNS3 router.
A traceroute to a google dns server revealed the works behind the scenes. It reach the 192.168.x.1 and THEN went to the 10.x.x.1. So my PC is like a proxy right?
So I am kind of new to networking and I'm just interested in the client/server architecture. Let's say you developed a program and the client version ran on a computer and the server version on the server(obviously). In order for the client to connect to the server, it would have to know the ip address of the server (and the port attached so it can be routed to the correct computer/program). Does that mean that the server's ip address can not change? Would you have to specifically tell your ISP to keep the ip address static? Because if both the client and server ip addresses change, then they would have no way to connect and the program wouldn't work... in other words there has to be one constant. When you sign up for a VPS do they give you a static ip address you can bind to from the client version? Thanks!
In order for the client to connect to the server, it would have to know the ip address of the server (and the port attached so it can be routed to the correct computer/program).
Correct.
Does that mean that the server's ip address can not change?
No. In fact, IPs can change at any time. Most servers that are exposed to the public Internet have a static domain name registered in the Internet's DNS system. A client asks DNS to resolve the desired domain name to its current IP address, and then the client can connect to it. But even in private LANs, most routers act as a local DNS server, allowing machines on the same network to discover each other's IP by machine name.
The OS typically handles DNS for you. A client can simply call gethostbyname() or prefferably getaddrinfo(), and the OS will perform DNS queries as needed on the client's behalf and return back the reported IP(s).
Would you have to specifically tell your ISP to keep the ip address static?
You can, but that usually costs extra. And it is not necessary if your server is registered in DNS. And there are free/cheap DNS systems that work with servers that do not have a static IP.
Because if both the client and server ip addresses change, then they would have no way to connect and the program wouldn't work...
That is where DNS comes into play.
in other words there has to be one constant.
A registered domain name that can be resolved by DNS.
When you sign up for a VPS do they give you a static ip address you can bind to from the client version?
It depends on the VPS service, but a more likely scenario would be you are assigned a static sub-domain within the VPS service's main domain. For example, myserver.thevps.com. Or, if you buy your own domain (which can be done very cheaply from any number of providers), you can usually link it to the DNS server operated by your VPS service.
Sorry if I have this in the wrong community but I'm hoping one of you can help me out anyway.
I have a web hosting account with a UK company who I'm happy with, but I'd like to set up a little hosting account from my laptop, just to see if it's possible and easy enough to do really.
Trouble is I've been doing a lot of research online but coming up empty whenit comes to more of a "complete guide". Do any of you know of a good resource for setting up a home server for publishing "Live" websites with custom TLD domain names? I have a localhost server running and files hosted on there but I'm really looking for help with the IP and DNS parts for the custom domains.
For reference, I have a machine running Win7, Appserv 2.5.10, UK broadband and a .co.uk domain name registered with 123-reg.
Any help would be hugely appreciated.
You'll need to:
Point your domain to your laptop.
If you get static public IP address from your ISP, then you can just point the A record to this IP address.
Where do I set this A record? Almost all domain registrars give you a nameserver for free. You point your domain to their nameservers (generally ns1.somedomain.com and ns2.samedomain.com etc.). In the nameserver config, create a A (stands for authoritative) record and put in your static IP address.
What if my ISP doesn't give me an static IP address? This is where services like dyndns come into picture. They give you an agent that you'll install on your laptop, it detects the change in IP address and automatically updates the Nameservers accordingly. There are some free variants of dyndns as well if you don't want to spend money on this.
But my laptops IP address is something like 192.168.x.x and my site runs on localhost (127.0.0.1)? Your laptop is most likely NATed. Think about your public IP address to be that of your router. You will need to forward any connection coming to your router on port 80 or 443 to your laptop's (192.168.x.x) corresponding ports. This is called Port-Forwarding and all routers support this. Port-Forwarding is done by logging on to the admin interface of your router (Many times its at http://192.168.0.1 or http://192.168.1.1).
But again my application is accessible at localhost? You need to make sure your apache/nginx listens on 0.0.0.0 or atleast 192.168.x.x interface. This is how computers outside your laptop will be able to make connection to your laptop on port 80/443.