Tag Info

Hot answers tagged

15

Ugh. I don't normally chime in after so many good people have answered, but I can't entirely agree with any of the answers so far posted. After 20 years of DNS admin, here's my take: Should DNS just be outsourced? No. It's perfectly fine to run your own DNS server (though a static IP address is to my mind essential), and as Vasili notes, it's a good ...


12

There's nothing wrong with having two services go to the same IP address, as long as the destination ports do not conflict with one another. In this case, you would be using port 53 for DNS, and port 80 for your web server. You can also have both (or all) of your nameservers set to the same IP address.* You will need to set up an authoritative DNS ...


4

RFC 3118 allows for authentication in DHCP messages although AFAIK it isn't implemented in the current DHCP servers. If you want to secure your network a better approach is IEEE_802.1X where clients must authenticate themselves to the switch port before they can access the network. That means that even if an unauthenticated system is configured with a ...


3

EDIT: Moderator asked me for a more verbose answer. Heres the rephrased one: I suggest you make a DMZ, with a public IP pointed to a single host internally. Have a look in your local router documentation, to see how this is accomplished, as it varies from each brand and I'm unfamiliar with Cisco SOHO routers. For reference, heres a link to the ...


3

You will need to configure IP-Based Virtual Host. You can do that by editing your apache/httpd.conf file, add something like this: <VirtualHost 100.100.100.100:80> ServerAdmin rubberduck@mydomain.com DocumentRoot /home/admin/domains/mydomain.com/public_html ServerName site.mydomain.com ErrorLog /var/log/httpd/logs/site/error_log TransferLog ...


3

Yes, DNS and web server can be on the same IP. However the way DNS is usually configured, it has to be a static IP. Running a web server on a dynamic IP is simple, as long as the DNS server supports it. Moreover, you really should have two DNS servers with IPs in different subnets. So it may be simpler to just host you domain at one of the many free DNS ...


2

The reason for this is that you actually have two routing table entries. First there is the default, which points at the gateway 192.168.2.1 in 192.168.2.0/24 network, and then there is the network route for network for interface eth0 (ie. 192.168.2.0/24) as well. If you delete the network route of an active, it effectively shuts it down. In this particular ...


2

What you actually want is a One-To-One NAT. This allows the router to translate an incoming public address with a private IP within your network. These instructions provide detailed instructions, but the jist of it is to enable One-To-One NAT, give the external and internal IP, and set the range length to "1". When done, you should be able to access your ...


1

If you're talking about "unresolved IP's" as seen in AwStats, then no. There is no way to do this from a firewall. "Unresolved" refers to the fact that the IP address has no reverse-dns set up. This is becoming the norm for "non servers"! This means IF you could block based on this, you'd block a lot of DSL lines and other home-user connections. ...


1

After a lot of testing, i must conclude that you cannot do this. It IS possible to dynamically change myhostname, it just doesn't affect the Received header. With a test having banner use $myhostname, i can see that it changes when i use -o myhostname=test.test.test but the received header does not. I tried using, in main.cf mydomain=test.test.test ...


1

No it will not, you can have as many as you want


1

Your assumption that pointing a "nameserver" for a domain to an IP address is correct. Porting the IP over while "possible" does not sound like you meet the requirements to achieve this. You need to do this in stages. The first of which is getting the nameserver for each domain pointed to a DNS record which resolves to the same IP address they use today. ...


1

First of all, you cannot bring the IP address along as you move to another hosting provider. IP addresses can only be moved between hosting providers, if you have a block of addresses, which was large enough to be announced over BGP. Any approach you take to moving would require a transition period where you are using one IP at the current hosting provider ...


1

You have to use a Dynamic DNS solution for this. You could use a DNS provider or configure your own Dynamic DNS server (there are a lot of tutorials for this). There are also scripts for using Route53 for this.


1

The Private IP is not accessible from outside the AWS network and is only useful when you have a cluster of EC2 instances for communication between them with-in your security group. You could assign a Elastic IP to the instance or use a Dynamic DNS Solution.


1

You need a NAT and port forwarding... PUBLIC IP | ----------------- | NAT | ----------------- | | TCP 80 | UDP 53 | | | Ubuntu Everything else Server Private IP Private IP You have both the nameserver and the webserver on the Ubuntu box. So your NAT router ...


1

You forget to mention what SMTP server you are using. If using Postfix you'll have some build-in features like http://www.postfix.org/postconf.5.html#smtpd_client_message_rate_limit to reduce the number of messages a client can send along with http://www.postfix.org/postconf.5.html#anvil_rate_time_unit to specify a period of time to monitor. As far as i ...


1

Yes, it is. Just use 0.0.0.0 for a binding address in your MySQL configuration file (e.g. /etc/mysql/my.cnf) as follows: bind-address = 0.0.0.0 If the address is 0.0.0.0, the server accepts TCP/IP connections on all server host IPv4 interfaces. Furthermore if the address is ::, the server accepts TCP/IP connections on all server host IPv4 and IPv6 ...


1

Also make sure Route table of VPC is set to enable IP address outside the VPC (0.0.0.0/0) to flow from the subnet to the Internet gateway. Navigate to VPC > Route Tables ; Route tab. Check Destination is 'mapped' to Target Internet Gateway Id (apart from local).


1

Your iptables rules are broken in multiple ways. First of all, your POSTROUTING chain has two rules, but the first one matches every packet, so the second rule is never used. Secondly, your SNAT and MASQUERADE rules should only be applied to packets leaving on eth0. But since 212.235.19.203 is allocated to just one machine, you may be better off not using ...


1

This is not generally done by pinging or ARP trickery. It's done by paperwork. Every request for IPv4 address assignments requires detailed justification, showing that existing addresses are fully utilized and that (in the case of ARIN) the new assignment will be 80% utilized within 30 days. See the ARIN Number Resource Policy Manual for complete details. ...


1

This is no problem technically speaking. But that's not what you want for your "home server" needs. Register yourself to some DynDNS service (DynDNS, no-ip, etc...) and point your domain there, thats it. Don't run a DNS Server if you don't know what you are doing. In your case it is also not needed to run one yourself.



Only top voted, non community-wiki answers of a minimum length are eligible