
Registered since September 28th, 2017
Has a total of 4246 bookmarks.
Showing top Tags within 12 bookmarks
howto information development guide reference administration design website software solution service product online business uk tool company linux code server system application web list video marine create data experience description tutorial explanation technology build blog article learn world project boat download windows security lookup free performance javascript technical control network beautiful support london tools course file research purchase library programming image youtube example php construction html opensource quality install community profile computer feature power browser music platform mobile work user process manage database share hardware professional buy industry internet dance advice installation developer 3d material search camera access customer travel test standard money documentation review css engineering webdesign engine develop device photography digital api speed source program management phone discussion question event client story simple water marketing app content yacht setup package fast idea interface account communication cheap script compare study market easy live google resource operation startup monitor training
Tag selected: dns.
Looking up dns tag. Showing 12 results. Clear
Saved by uncleflo on December 23rd, 2018.
When setting up the NAS, you need to enter in a server name. This becomes the hostname. How can I set a FQDN (i.e. NAS-Store.example.com) without it being wiped out all the time? You can just setup a ddns name and use it to get access (I'm guessing you wanna use that name to gain outside access to your NAS). There is a DDNS tab in Control Panel > External Access. Register your name there. I don't need to worry about DDNS. That is not an issue. As I run an internal DNS on my network, I can type in the FQDN of the NAS and get to it OK. That's all fine. I would just like to be able to give the NAS an FQDN and an SSL certificate to match it, so I do not get any warnings that the cert is incorrect for the NAS when I have external clients use the Cloud Station. I don´t you buy a domain name, setup it up by using DynDns client and give the domain name to your clients to connect to, and then set your internal DNS with that same domain name to point to the internal IP, and also set the name of the NAS with that domain name.
setup cloud clarify configure resolve domain server reply question answer suggestion administrator administration nas synology file share topic dns name ip access external
Saved by uncleflo on July 18th, 2016.
Open-Xchange is the pioneer of open and trusted software and solutions for service providers worldwide who are challenged with extending value and innovation
api app analyst business dns development germany software suite tools video tutorial reseller engage customer trust telecommunication provide saas work individual email freedom controldata
Saved by uncleflo on April 2nd, 2015.
Domain uncleflo.com is not listed in the top million list of Alexa. uncleflo.com is not listed in the top million list of Quantcast. It is not listed in the DMOZ directory. This domain has no WOT reputation. This domain is hosted by NatCoWeb Corp. (AS46636). The first DNS server is ns1.6sync.net. The current IPv4 address is 204.62.14.86.
tcp util whois ip domain lookup registration dns reputation browse utility information alexa quantcast directory
Saved by uncleflo on August 19th, 2013.
As you probably already know, one of the main problems when you’re doing multiple projects is to organize them properly, first for fast local testing of changes, second for your own sake, to not get lost on your own computer. One more problem are the testing local domains. Well, the easiest way when you create a project is to create a new project folder, put a new domain (and every subdomain you’ll use) into your /etc/hosts file, create a new virtual host in the apache config, run a2ensite #### (or however you enable a new site on your distribution), restart the webserver… Which means, you need to do that everytime when you’re creating a new project. Not a very convenient way if you ask me, as you’re bloating your /etc/hosts file and your Apache2 virtualHost file(s).
host dns unlimited apache dnsmasq localhost name subdomain domain server local infrastructure administration
Saved by uncleflo on August 19th, 2013.
I do a lot of work with subdomains, managing them locally on my development and test machines has always been a bit of a pain. Going way back, I can remember manually editing the hosts file in system32\drivers\etc\ on Windows! On the Unix we have /etc/hosts. Unfortunately /etc/hosts doesn’t allow wildcard definitions for subdomains, so you have to manually specify each one.
host wildcard automatic dns edit add dnsmasq script linux database localhost file domain subdomain insert infrastructure bash administration
Saved by uncleflo on August 19th, 2013.
In a previous article, I talked about using subdomains in Rails 3. Since then, many people have elaborated on the topic. There's even been a great Railscast. I've found Tim Pope's post particularly useful. Basically, he has set up a domain name that resolves to locahost/127.0.0.1. This save you from having to specify subdomains in you /etc/hosts file - which is a hassle! I'd like to offer another alternative using Dnsmasq. With Dnsmasq, you can set up a simple DNS server locally, then you can use an apache virtual host to deal with wildcard domains.
guide wildcard dns domain subdomain linux blog dnsmasq howto administration
Saved by uncleflo on August 19th, 2013.
Since 12.04 NetworkManager needs dnsmasq-base as a dependency, If dnsmasq is installed ie apt-get install dnsmasq it will try to bind to port 53 which is already in use because of NetworkManager. To resolve first comment the dnsmasq line from networkmanager.
guide install port manager dns linux dnsmasq howto network software name subdomain server ubuntu
Saved by uncleflo on August 19th, 2013.
I want to setup my local development machine so that any requests for *.local are redirected to localhost. The idea is that as I develop multiple sites, I can just add vhosts to Apache called site1.local, site2.local etc, and have them all resolve to localhost, while Apache serves a different site accordingly.
site host development wildcard dns edit apache windows xp localhost winxp name server local question
Saved by uncleflo on August 19th, 2013.
Dnsmasq is a lightweight, easy to configure, DNS forwarder and DHCP server. It is designed to provide DNS and optionally, DHCP, to a small network. It can serve the names of local machines which are not in the global DNS. The DHCP server integrates with the DNS server and allows machines with DHCP-allocated addresses to appear in the DNS with names configured either in each host or in a central configuration file. Dnsmasq supports static and dynamic DHCP leases and BOOTP/TFTP for network booting of diskless machines.
dns dnsmasq linux network ip file centos name config server configuration debian infrastructure administration
Saved by uncleflo on July 23rd, 2013.
Before you edit any files, you'll need to obtain some information. Log into the Linode Manager and click the "Remote Access" tab. You'll find your IP addresses (both public and private, if you have a private IP assigned), gateways, netmasks and DNS resolvers. Keep this information handy, because you'll need to refer to it as you configure your Linode's network settings. Since Linodes only have one virtual ethernet interface (eth0), you'll need to assign additional IPs to aliases on that interface. This means you'll append a colon and a number to the interface name. For these examples, the aliases are numbered in the order they were given, but most outbound connections will originate from the IP assigned to the eth0 interface. If you need server daemons to bind to a particular IP address, you'll need to specify the correct IP in their configuration files.
guide information host static manager dns resolution dnsmasq network private ip linode netbios name config server public configure administration
Saved by uncleflo on January 5th, 2013.
While name resolution and browsing are not difficult to configure, some complexity is introduced by the variety of available name-resolution systems. Historically, Unix and other TCP/IP users have moved from a flat hosts file to the Domain Name System, with the Network Information System being another popular choice. Meanwhile, Microsoft has moved from a broadcasting system to a simple, LAN-only name server called WINS and ultimately to DNS. The reason for going over that history is that all previous systems of name resolution are still in use today! Finding a host is so crucial to networking that sites want robust (if limited) name-resolution systems to fall back on in case the main system fails. Browsing is also complicated by the frequent need to show hosts in other subnets. This chapter shows you how to configure your network to handle name resolution and browsing any way you want.
information guide windows microsoft linux samba share setup server file dns wins host name resolution browse network
Saved by uncleflo on December 8th, 2009.
This tutorial will explain how to setup Windows Server 2008 Domain Controller and DNS
Server.
guide howto tutorial windows network controller server windows2008 server2008 dns domain
No further bookmarks found.